Dear Folks, |
Re: Add modules to CPS non-manually Mathias Mamsch, IT-QBase GmbH, Consultant for Requirement Engineering and D00RS |
Re: Add modules to CPS non-manually Your approach looks reasonable to me. Manually create one CPS module and make sure it works by creating a CP. Edit the partner, find the CP, delete its outgoing link then delete the CP. Clone the CP module. Create the link set. I'm guessing you didn't clone it right. Your 'clone' will need to copy all Proposal 1 objects, and attr-types and attr-defs and views (not links nor external links). Sounds like you really want to just copy it, so long as you haven't created any CPs in it already ..err.. it doesn't have any CPs in it. You will need to set shared sections on all level 1 objects in the new CPS module (these represent each configured CPS user). You will need to create a link-set as you have done. You should verify that that particular new CPS module has no other link-sets in that link module, which perhaps can get created when you 'copy' a CP module with active CPs. Did your original CPS module work (Proposals 1)? Did you open the other Req module, then clone its CPS module? Perhaps you need to close the Req and re-open it after creating the link-set. Its good practice, again hypothetically, to rename the CPS module; so if your Req module is "System Reqs" perhaps its CPS partner should have name "CPs System Reqs". We've done that ..err.. in a test environment ... with no problems. Yes, the CPS gui uses the existence of the Link-Set to determine the partner module.
|